Description |
|---|
Parameters:
var_tso_id
free defined number of the test to be able to identify the packet which is sent by the tester and to identify the packet which is sent by the IUT in response to the packet generated following to the TSO.
var_lap:
defines which type of access code is used by the IUT in its ID packets (general inquiry LAP or reserved/dedicated LAP)
var_first_train:
in case of 79 channel hopping system this parameter defines if the tester starts following the A train or the B train
1= train A, 2= train B
in case of 23 channel hopping sequence this parameter is not necessary because only A train exits
var_n_inquiry:
in case of 79 channel hopping sequence this parameter defines how many times a train shall be repeated before switching to the other train,
in case of 23 channel hopping sequence defines how many times a single train shall be repeated.
var_start_scan_offset:
offset of the tester where it starts scanning for the IUT's ID packets when the tester is in inquiry scan mode. The tester starts with k-6 which is the offset value 14. The following rule is applied:
k-8 = "16",
k-7 = "15"
k-6 = "14"
......
k+7 = "1".
var_number_of_inquiry_sequences:
var_inquiry_duration:
defines how many the inquiry instances length (specified in HCI_Inquiry sent to the tester shall scan
IUT) plus 30 seconds (approximately half of maximum inquiry length) in slots
Procedure:
The IUT uses the estimate CLKN of the tester (in case of 79 channel hopping system) and because of this the tester does not know exactly the sequence of the IUT when it starts the first (inquiry) ID-packet. The tester therefore does not wait for the ID-packet at the first possible frequency k-8 but on a frequency e.g. k-6. Then the tester scans constantly on this defined first inquiry frequency (var_start_scan_offset) to syncronize on the IUT. Afterwards the tester follows the inquiry sequence of the IUT.
The parameter "var_n_inquiry" defines the minimum number of train repetitions. In the first train the number of minimum required ID packet is reduced by (16 - var_start_scan_offset) since the first packages are missing. After the minimum number of ID packets in the first A train are counted (var_n_inquiry * 16 - (16 - var_start_scan_offset)) the tester switches to the next train and counts again the total number of (var_n_inquiry * 16) packets. After this this, the tester again switches to train A until 'var_inquiry_duration' slots has been reached. At the current inquiry instance is finished.
If end, the IUT performs periodic inquiry, tester sends a POLL packet with the channel access code generated using the LAP of the BD_ADDR's tester has in order to distinguish between different inquiry instances, and establish a trigger for the procedure described in end of the previous paragraph will be repeated until var_number_of_inquiry_sequences number P_LC component of inquiry instances are counted.
the test case.
Return value:
When the TSO finishes successfully the value of the return parameter will be TRUE.
If an error occurs the TSO will finish and the value of the return parameter will be FALSE.
|
|